System and method for securing a private key transaction within blockchain

ABSTRACT

A system and method for securing a private key transaction within blockchain that include receiving an input for initiating a financial transaction between a sender and a recipient. The system and method also include processing a secure wallet that includes transaction data associated with the financial transaction. The system and method additionally include generating a private key for the sender and a private key for the recipient. The system and method further include communicating the transaction data to complete the financial transaction using the blockchain.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims priority to U.S. Provisional Application Ser.No. 62/897,572 filed on Sep. 9, 2019, which is expressly incorporatedherein by reference.

BACKGROUND

Many individuals are increasing utilizing electronic systems to completemonetary transactions between one another and between themselves andvendors, retailers, banking instructions and the like. In many of thetransactions blockchain technology may be used to complete thetransactions. The blockchain technology may include blocks that maystore information about transactions that may include the participantsof the transaction (e.g., user 1 and user 2, user 1 and vendor), date,time, and dollar amount of each transaction. When a block is added tothe blockchain it may become publicly available for anyone to view. Eachcomputer in a blockchain network has its own copy of the blockchain.Accordingly, there may be a large amount of copies of the sameblockchain. Much of the burden for ensuring that each financialtransaction is secure is placed upon one type of technology that may beutilized by the blockchain such as the completion of digital signatures.

BRIEF DESCRIPTION

According to one aspect, a computer-implemented method for securing aprivate key transaction within blockchain that includes receiving aninput for initiating a financial transaction between a sender and arecipient. The computer-implemented method also includes processing asecure wallet that includes transaction data associated with thefinancial transaction. The computer-implemented method additionallyincludes generating a private key for the sender and a private key forthe recipient. The private keys are securely exchanged for securevalidation of the financial transaction. The computer-implemented methodfurther includes communicating the transaction data to complete thefinancial transaction using the blockchain.

According to another aspect, a system for securing a private keytransaction within blockchain that includes a memory storinginstructions when executed by a processor cause the processor to receivean input for initiating a financial transaction between a sender and arecipient. The instructions also cause the processor to process a securewallet that includes transaction data associated with the financialtransaction. The instructions additionally cause the processor togenerate a private key for the sender and a private key for therecipient. The private keys are securely exchanged for secure validationof the financial transaction. The instructions further cause theprocessor to communicate the transaction data to complete the financialtransaction using the blockchain.

According to yet another aspect, a non-transitory computer readablestorage medium storing instructions that when executed by a computer,which includes a processor perform a method that includes receiving aninput for initiating a financial transaction between a sender and arecipient. The method also includes processing a secure wallet thatincludes transaction data associated with the financial transaction. Themethod additionally includes generating a private key for the sender anda private key for the recipient. The private keys are securely exchangedfor secure validation of the financial transaction. The method furtherincludes communicating the transaction data to complete the financialtransaction using the blockchain.

BRIEF DESCRIPTION OF THE DRAWINGS

The novel features believed to be characteristic of the disclosure areset forth in the appended claims. In the descriptions that follow, likeparts are marked throughout the specification and drawings with the samenumerals, respectively. The drawing figures are not necessarily drawn toscale and certain figures can be shown in exaggerated or generalizedform in the interest of clarity and conciseness. The disclosure itself,however, as well as a preferred mode of use, further objects andadvances thereof, will be best understood by reference to the followingdetailed description of illustrative embodiments when read inconjunction with the accompanying drawings, wherein:

FIG. 1 is a schematic view of an exemplary operating environment forsecuring a private key transaction within blockchain according to anexemplary embodiment of the present disclosure;

FIG. 2 is a schematic view of a plurality of modules of the securetransaction that may execute computer-implemented instructions forsecuring a private key transaction within blockchain according to anexemplary embodiment of the present disclosure;

FIG. 3 is a process flow diagram of a method for securing a financialtransaction between a sender and a recipient according to an exemplaryembodiment of the present disclosure; and

FIG. 4 is a process flow diagram of a method for secure a private keytransaction with blockchain according to an exemplary embodiment of thepresent disclosure.

DETAILED DESCRIPTION

The following includes definitions of selected terms employed herein.The definitions include various examples and/or forms of components thatfall within the scope of a term and that can be used for implementation.The examples are not intended to be limiting.

A “bus,’ as used herein, refers to an interconnected architecture thatis operably connected to transfer data between computer componentswithin a singular or multiple systems. The bus may be a memory bus, amemory controller, a peripheral bus, an external bus, a crossbar switch,and/or a local bus, among others. The bus may also be a vehicle bus thatinterconnects components inside a vehicle using protocols such asController Area network (CAN), Media Oriented System Transport (MOST),Local Interconnect Network (LIN), among others.

“Computer communication,” as used herein, refers to a communicationbetween two or more computing devices (e.g., computer, personal digitalassistant, cellular telephone, network device) and may be, for example,a network transfer, a file transfer, an applet transfer, an email, ahypertext transfer protocol (HTTP) transfer, and so on. A computercommunication may occur across, for example, a wireless system (e.g.,IEEE 802.11), an Ethernet system (e.g., IEEE 802.3), a token ring system(e.g., IEEE 802.5), a local area network (LAN), a wide area network(WAN), a point-to-point system, a circuit switching system, a packetswitching system, among others.

An “input device,” as used herein may include devices for controllingdifferent vehicle features which include various vehicle components,systems, and subsystems. The term “input device” includes, but it notlimited to: push buttons, rotary knobs, and the like. The term “inputdevice” additionally includes graphical input controls that take placewithin a user interface which may be displayed by various types ofmechanisms such as software and hardware based controls, interfaces, orplug and play devices.

A “memory,” as used herein may include volatile memory and/ornonvolatile memory. Non-volatile memory may include, for example, ROM(read only memory), PROM (programmable read only memory), EPROM(erasable PROM) and EEPROM (electrically erasable PROM). Volatile memorymay include, for example, RAM (random access memory), synchronous RAM(SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rateSDRAM (DDR SDRAM), and direct RAM bus RAM (DRRAM).

A “module,” as used herein, includes, but is not limited to, hardware,firmware, software in execution on a machine, and/or combinations ofeach to perform a function(s) or an action(s), and/or to cause afunction or action from another module, method, and/or system. A modulemay include a software controlled microprocessor, a discrete logiccircuit, an analog circuit, a digital circuit, a programmed logicdevice, a memory device containing executing instructions, and so on.

An “operable connection,” as used herein may include a connection bywhich entities are “operably connected”, is one in which signals,physical communications, and/or logical communications may be sentand/or received. An operable connection may include a physicalinterface, a data interface and/or an electrical interface.

An “output device,” as used herein may include devices that may derivefrom vehicle components, systems, subsystems, and electronic devices.The term “output devices” includes, but is not limited to: displaydevices, and other devices for outputting information and functions.

A “processor,” as used herein, processes signals and performs generalcomputing and arithmetic functions. Signals processed by the processormay include digital signals, data signals, computer instructions,processor instructions, messages, a bit, a bit stream, or other meansthat may be received, transmitted and/or detected. Generally, theprocessor may be a variety of various processors including multiplesingle and multicore processors and co-processors and other multiplesingle and multicore processor and co-processor architectures. Theprocessor may include various modules to execute various functions.

I. System Overview

Referring now to the drawings, wherein the showings are for purposes ofillustrating one or more exemplary embodiments and not for purposes oflimiting the same, FIG. 1 is a schematic view of an exemplary operatingenvironment 100 for securing a private key transaction within blockchainaccording to an exemplary embodiment of the present disclosure. In anexemplary embodiment, the operating environment 100 may include a secureserver infrastructure (secure server) 102 that may be configured executea blockchain private key secure transaction application (securetransaction application) 104. As discussed below, the secure transactionapplication 104 may enable enhanced secure financial transactionsbetween a sender 106 (senders, users, persons initiating electronicsending of funds) and a recipient 108 (users, beneficiaries, vendors,retailers, banking instructions, etc.).

As discussed in more detail below, the secure transaction application104 may be configured to receive an input that may be provided by thesender 106 to initiate a financial transaction between the sender 106and the recipient 108 of funds. The secure transaction application 104may be configured to process a secure wallet 110 (e.g., virtual wallet,virtual secure account) that may be stored in a secured location, asdiscussed below. The secure transaction application 104 may additionallybe configured to collect funds from the sender 106 that may be storedwithin the secure wallet 110.

The secure transaction application 104 may be additionally configured togenerate a private encrypted data key (private key) 112 a that may beassigned to the sender 106 of the funds and a private key 112 b that maybe assigned to the recipient 108 of the funds. Each of the private keys112 a, 112 b may be encrypted with a numerical encrypted key code oralpha-numerical encrypted key code that may not be publicallyaccessible. As discussed below, the private keys 112 a, 112 b may beexchanged as ownership credentials to securely validate the financialtransaction between the sender and the recipient.

In one embodiment, the secure transaction application 104 may also beconfigured to generate a public key 114 that may be passed to theblockchain technology provider(s) (not shown) through a blockchaininfrastructure 116. The public key 114 may include basic informationpertaining to the account information that may be utilized by theblockchain technology provider(s) to pass the financial transactionthrough a blockchain technology via the blockchain infrastructure 116 tocomplete the financial transaction in an encrypted and secure mannerusing blockchain.

With particular reference to FIG. 1, the secure server 102 may include aprocessor 118. The processor 118 may operably control one or morecomponents of the secure server 102. In an exemplary embodiment, theprocessor 118 may be configured to execute the secure transactionapplication 104. The processor 118 may be configured to execute one ormore operating systems, financial system and subsystem executableinstructions, and the like. The processor 118 may also includerespective internal processing memory, an interface circuit, and buslines for transferring data, sending commands, and communicating withthe plurality of components of the secure server 102.

In one embodiment, the processor 118 may be operably connected to amemory 120 of the secure server 102. The memory 120 may be configured tostore data files associated with one or more applications, operatingsystems, financial systems, financial system user interfaces, includingbut not limited to data files of the secure transaction application 104.In one embodiment, the memory 120 may be configured to store a secureencrypted data environment 122 of the secure transaction application104. The secure encrypted data environment 122 may be configured as anencrypted data store that may be accessible based on a selectively andrandomly encrypted passcode that may be processed by the processor 118at one or more periods of time (e.g., every thirty seconds).

The secure encrypted data environment 122 may be utilized as anencrypted data container that may allow the secure transactionapplication 104 to securely store one or more secure wallets 110 thatare associated with respective financial transactions. Each respectivesecure wallet 110 may be configured as an encrypted data packet that maystore transaction data that may include, but may not be limited to, amonetary transfer amount, account information, wiring information,routing information, and the like associated with the financialtransaction from the sender 106 to the recipient 108. As discussedbelow, the secure transaction application 104 may be configured toaccess the secure encrypted data environment 122 to store one or moresecure wallets 110 that are processed by the application 104. Theapplication 104 may also access the respective secure wallets 110 oncesecure validation is completed based on an exchange of the private keys112 a, 112 b.

In an exemplary embodiment, the memory 120 may additionally beconfigured to store a user data repository 124. The user data repository124 may include data that pertains to one or more users that may utilizethe secure transaction application 104 to securely complete financialtransactions. Upon the sender 106 initially utilizing the securetransaction application 104 to initiate a financial transfer, the securetransaction application 104 may present a user profile setup userinterface that may be presented to the sender 106 and/or the recipient108 during an initial usage and/or one or more subsequent usages of thesecure transaction application 104.

The user profile setup user interface may be utilized to input profileinformation associated with the sender's name, address, bankinginstitution(s), and the like. The user interface may also allow therecipient 108 to link one or more bank accounts to the securetransaction application 104. Similarly, the secure transactionapplication 104 may present a user interface to the recipient 108 via aportable device (not shown) or computing infrastructure (not shown) usedby the recipient 108 to input profile information associated with therecipient's name, address, banking institution(s), and the like.Accordingly, user profiles 130 a, 130 b respectively associated with thesender 106 and the recipient 108 may be respectively populated with datathat pertains to information associated with one or more financialaccounts (e.g., bank account numbers, fund account information), wiringinformation, routing information, transfer timeframe information, andthe like.

The user profile 130 a associated with the sender 106 may also includesender identification (e.g., name, address, phone number(s) of thesender 106). Similarly, the user profile 130 b associated with therecipient 108 may include also recipient information (e.g., name,address, phone number(s) of recipient 108). As discussed below, the userprofiles 130 a, 130 b associated with the sender 106 and the recipient108 may be accessed to utilize the information stored within the userprofiles 130 a, 130 b during a fulfillment of one or more securetransactions between the sender 106 and the recipient 108. For example,such information may be securely stored and utilized when processing thepublic key 114 to thereby populate the public key 114 that may be passedto the blockchain upon the secure exchange of private keys 112 a, 112 bthat are assigned to the sender 106 and the recipient 108.

With continued reference to the secure server 102, the processor 118 ofthe secure server 102 may also be operably connected to a communicationunit 126. The communication unit 126 may include one or more networkinterface cards (not shown) that may be configured to connect to one ormore computing systems through an internet cloud (not shown). Suchcomputing systems may include, but may not be limited to, portabledevices used by the sender 106 and the recipient 108 and/or computingequipment used by the sender 106 and the recipient 108. In oneembodiment, the secure transaction application 104 may be configured toutilize the communication unit 126 to present the user interface of theapplication 104 to the sender 106 and/or the recipient 108 uponreceiving an input from the sender 106 to initiate a financial transferof funds to the recipient 108.

The user interface may be utilized during an initial use of the securetransaction application 104 to input profile information associated withthe sender's and recipient's name, address, banking instruction(s), andthe like. The user interface may also allow the sender 106 and/or therecipient 108 to link one or more respective bank accounts to the securetransaction application 104. During the initial and subsequent uses ofthe secure transaction application 104 the user interface may allow thesender 106 to input a monetary transfer amount (e.g., dollar amount)that the sender 106 may wish to transfer. The secure transactionapplication 104 may also present the transfer amount inputted by thesender 106 to the recipient 108 to accept or deny the transfer. If thetransfer is accepted by the recipient 108, the secure transactionapplication 104 may be configured to process the secure wallet 110, asdiscussed below.

In one or more embodiments, the secure transaction application 104 mayinclude an encrypted key generator 128. The encrypted key generator 128may be configured to generate the private key 112 a that may beassociated with the sender 106 and the private key 112 b that may beassociated with the recipient 108. The encrypted key generator 128 mayprocess the private keys 112 a, 112 b with a numerical encrypted keycode (e.g., n digit alpha-numeric code) or alpha-numerical encrypted keycode that may not be publically accessible.

The private keys 112 a, 112 b may be exchanged as ownership credentialsto securely validate the financial transaction between the sender 106and the recipient 108 without each of them being able to access theprivate keys 112 a, 112 b. In one configuration, the secure transactionapplication 104 may utilize the communication unit 126 to transfer thesender's private key 112 a to the recipient 108 to be authenticatedwithout the recipient 108 being able to access the sender's private key112 a. Likewise, the secure transaction application 104 may utilize thecommunication unit 126 to transfer the recipient's private key 112 b tothe sender 106 to be accepted and authenticated without the sender 106being able to access the recipient's private key 112 b.

In one configuration, the encrypted key generator 128 may also beconfigured to process the public key 114 that may be passed to theblockchain technology provider(s) through the blockchain infrastructure116. The public key 114 may include basic information pertaining toaccount information using an elliptical curve process. In oneconfiguration, the public key 114 may include selected information(e.g., encrypted financial data) from the private keys 112 a, 112 b andmay be utilized by the blockchain technology provider(s) to pass thefinancial transaction through a blockchain technology to complete thefinancial transaction in an encrypted and secure manner using theblockchain.

In one or more embodiments, the blockchain infrastructure 116 may beconfigured to include one or more externally hosted computing systemsthat may be owned, operated, and/or hosted by one or more blockchaintechnology providers. In one embodiment, upon securely validating thefinancial transaction between the sender 106 and the recipient 108, thesecure transaction application 104 may utilize the communication unit126 to transfer the public key 114 and transaction data associated withthe financial transaction to the blockchain infrastructure 116 to passthe financial transaction through a blockchain technology and tocomplete the financial transaction in an encrypted and secure mannerusing blockchain.

II. The Private Key Secure Transaction Application and Methods Executedby the Application

The secure transaction application 104 and its components will now bediscussed in more detail according to an exemplary embodiment and withcontinued reference to FIG. 1. In one or more embodiments, the securetransaction application 104 may be stored on the memory 120 of thesecure server 102 and may be executed by the processor 118 of the secureserver 102. In another embodiment, the secure transaction application104 may be stored on an externally hosted server infrastructure (notshown) or one or more computing systems of the blockchain infrastructure116 and may be accessed by the secure server 102 through thecommunication unit 126 to be executed by the processor 118 of the secureserver 102. In yet some additional embodiments, the secure transactionapplication 104 may be stored on the secure server 102, one or morecomputing devices of the blockchain infrastructure 116, and/or theportable device and/or computing infrastructure used by the sender 106and/or the recipient 108.

FIG. 2 is a schematic view of a plurality of modules 202-208 of thesecure transaction application 104 that may execute computer-implementedinstructions for securing a private key transaction within blockchainaccording to an exemplary embodiment of the present disclosure. In anexemplary embodiment, the plurality of modules 202-208 may include atransaction initiation module 202, a secure wallet processing module204, a key execution module 206, and a transaction execution module 208.It is appreciated that the secure transaction application 104 mayinclude one or more additional modules and/or sub-modules that areincluded in addition to or in lieu of the modules 202-208.

In an exemplary embodiment, the transaction initiation module 202 of thesecure transaction application 104 may be configured to present a securetransaction initiation user interface that may be utilized by the sender106 and/or the recipient 108 to initiate a secure transaction throughthe secure transaction application 104. In particular, the securetransaction initiation user interface may be presented to the sender 106(e.g., through the senders portable device) to initiate a financialtransaction (e.g., that is initiated by the sender 106) that may beutilized to securely transfer an amount of funds to the recipient 108.Upon the sender 106 inputting an input user interface icon that may bepresented as part of the secure transaction initiation user interface toinitiate the secure financial transaction, the secure financialtransaction initiation user interface may be presented to the recipient108 (e.g., through the recipient's portable device) to accept or reject(e.g., through the presentation of respective user interface imputableicons) the initiation of the financial transaction. In one embodiment,the transaction initiation module 202 may determine when the sender 106initiates a financial transaction of funds and when the recipient 108accepts the initiation of the financial transaction of funds from thesender 106 to the recipient 108.

In another embodiment, in circumstances in which the recipient 108 wouldlike to initiate a request to receive funds from the sender 106 (e.g.,for a transaction, for a debt, etc.), the secure transaction initiationuser interface may be utilized by the recipient 108 to invite the sender106 to initiate the financial transaction of funds between the sender106 and the recipient 108. In particular, based on an input of aninitiation user input icon, the secure transaction initiation userinterface may be presented to the recipient 108 to send a transactioninitiation invitation (e.g., through the recipient's portable device) toinitiate a financial transaction of a particular monetary amount thatmay be utilized to securely transfer the particular monetary amount offunds (e.g., dollar amount) to the recipient 108 from the sender 106.

Upon the recipient 108 inputting an input user interface icon that maybe presented as part of the secure transaction initiation user interfaceto send the transaction initiation invitation, the secure financialtransaction initiation user interface may be presented to the sender 106(e.g., through the sender's portable device) to accept or reject (e.g.,through the presentation of respective user interface imputable icons)the initiation of the financial transaction of the particular monetaryamount. In one embodiment, the transaction initiation module 202 maythereby determine when the recipient 108 inputs the invitation for theinitiation of a secure transaction of funds to the sender 106 and if thesender 106 accepts the invitation to initiate the secure transaction offunds from the sender 106 to the recipient 108.

In one or more embodiments, during initial and subsequent uses of thesecure transaction application 104, the secure financial transactioninitiation user interface may allow the sender 106 to input a monetarytransfer amount or edit the monetary transfer amount that may bepre-inputted based on the acceptance of the recipient's transactioninitiation invitation. Accordingly, the monetary amount of funds thatthe sender 106 may wish to transfer to the recipient 108 may bedetermined by the transaction initiation module 202. Upon thedetermination of the transfer amount that the sender 106 may wish tosecurely transfer to the recipient 108, the transaction initiationmodule 202 may be configured communicate data pertaining to theinitiation of the secure transaction between the sender 106 and therecipient 108 and the monetary transfer amount to the secure walletprocessing module 204, the key execution module 206, and the transactionexecution module 208 of the secure transaction application 104.

In an exemplary embodiment, the secure wallet processing module 204 ofthe secure transaction application 104 may be configured to process asecure wallet 110 that may be utilized to complete the securetransaction between the sender 106 and the recipient 108. In oneconfiguration, upon the sender 106 initiating the secure transaction,the secure wallet processing module 204 may be configured to process thesecure wallet 110 that may be associated with the particular securetransaction between the sender 106 and the recipient 108. In oneembodiment, upon processing the secure wallet 110 associated with thesecure transaction between the sender 106 and the recipient 108, thesecure wallet processing module 204 may be configured to access thesecure encrypted data environment 122 stored on the memory 120 toanalyze the user profiles that may be associated with the sender 106 andthe recipient 108.

The secure wallet processing module 204 may be configured to retrieveinformation from the respective user profiles and may thereby populatethe secure wallet 110 with information that may be retrieved from therespective user profiles that are associated with the sender 106 and therecipient 108. Such information may include, but may not be limited to,information associated with one or more financial accounts (e.g., bankaccount numbers, fund account information), wiring information, routinginformation, sender identification (e.g., name, address, phone number(s)of the sender 106), recipient information (e.g., name, address, phonenumber(s) of the recipient 108), and the like that may be utilized astransaction information.

In one embodiment, upon processing and populating the secure wallet 110associated with the secure transaction between the sender 106 and therecipient 108, the secure wallet processing module 204 may be configuredto access the secure encrypted data environment 122 stored on the memory120 of the secure server 102. Upon accessing the secure encrypted dataenvironment 122, the secure wallet processing module 204 may beconfigured to store the secure wallet 110 within the secure encrypteddata environment 122.

In an exemplary embodiment, upon processing and storing the securewallet 110 the secure wallet processing module 204 may be configured tocollect transaction information associated with the particular securetransaction between the sender 106 and the recipient 108. As discussedabove, the secure encrypted data environment 122 may be configured as anencrypted data store that may be accessible based on a selectively andrandomly encrypted passcode that may be processed by the processor 118of the secure server 102 at one or more periods of time (e.g., everythirty-seconds).

Also as discussed, during initial and subsequent uses of the securetransaction application 104, the secure financial transaction initiationuser interface may allow the sender 106 to input a monetary transferamount or edit the monetary transfer amount that may be pre-inputtedbased on the acceptance of the recipient's transaction initiationinvitation. Accordingly, the monetary amount of funds that the sender106 may wish to transfer to the recipient 108 may be determined by thetransaction initiation module 202. Upon the determination of thetransfer amount that the sender 106 may wish to securely transfer to therecipient 108, the transaction initiation module 202 may be configuredcommunicate data pertaining to the initiation of the secure transactionbetween the sender 106 and the recipient 108 and the monetary transferamount to the secure wallet processing module 204. Accordingly, thesecure wallet processing module 204 may be configured to determinetransaction information associated with the sender 106 and the recipient108 and the monetary transfer amount that the sender 106 may wish tosecurely send to the recipient 108 based on communication received bythe transaction initiation module 202.

In one or more embodiments, the secure wallet processing module 204 mayadditionally be configured to access the secure encrypted dataenvironment 122 to an analyze the user profiles 130 a, 103 brespectively associated with the sender 106 and the recipient 108. Asdiscussed above, the user profiles 130 a, 130 b may be respectivelypopulated with data that pertains to information associated with one ormore financial accounts (e.g., bank account numbers, fund accountinformation), wiring information, routing information, transfertimeframe information, and the like. The secure wallet processing module204 may be configured to retrieve the information that may be associatedwith the one or more financial accounts, wiring information, routinginformation, transfer timeframe information and the like associated withthe sender 106 and the recipient 108.

In one embodiment, upon determining the monetary transfer amount andretrieving banking information from the user profiles 130 a, 130 b, thesecure wallet processing module 204 may be configured to store themonetary transfer amount and retrieving banking information astransaction information within the secure wallet 110. Accordingly, thesecure wallet 110 may include transaction information that pertains tothe secure transaction between the sender 106 and the recipient 108.Upon storing the transaction information associated with the securetransaction, the secure wallet processing module 204 may communicatedata pertaining to the processing and updating of the secure wallet 110to the key execution module 206 of the secure transaction application104.

In an exemplary embodiment, the key execution module 206 may beconfigured to utilize the encrypted key generator 128 to generate aprivate key 112 a for the sender 106 and a private key 112 b for therecipient 108. The generation of the private keys 112 a, 1122 b mayinclude computer processing of two separate private encrypted data keypackets that may be encrypted with a numerical key code oralpha-numerical key code. In one embodiment, upon the generation of therespective private keys 112 a, 112 b, the key execution module 206 maybe configured to execute the exchange of the private keys 112 a, 112 bas ownership credentials to securely validate the financial transactionbetween the sender 106 and the recipient 108.

The private keys 112 a, 112 b, may be exchanged as ownership credentialsand such an exchange may be utilized by the secure transactionapplication 104 to securely validate the financial transaction as asecure transaction between the sender 106 and the recipient 108. In oneconfiguration, the private keys 112 a, 112 b may not be visible to thesender 106 and the recipient 108. Accordingly, the key execution module206 may be configured to utilize the exchange of the private keys 112 a,112 b between the sender 106 and the recipient 108 without each of thembeing able to view the private keys 112 a, 112 b.

The private keys 112 a, 112 b may be exchanged as ownership credentialsto securely validate the financial transaction between the sender 106and the recipient 108. In particular, the key execution module 206 mayutilize the communication unit 126 of the secure server 102 to transferthe sender's private key 112 a to the recipient 108 electronically asencrypted application data. The key execution module 206 may alsoutilize the communication unit 126 to transfer the recipient's privatekey 112 b to the sender 106 electronically as encrypted applicationdata.

In one embodiment, upon the successful exchange of private keys 112 a,112 b between the sender 106 and the recipient 108, through the securetransaction application 104, the key execution module 206 may beconfigured to present private key exchange confirmation user interfacesto the sender 106 and the recipient 108 through respective portabledevices and/or computing infrastructure used by the sender 106 and therecipient 108. The key execution module 206 may also be configured toencrypt the respective private keys 112 a, 112 b to financial recordsthat are associated with the financial transaction between the sender106 and the recipient 108.

In an exemplary embodiment, upon the exchange of the private keys 112 a,112 b and the encrypting of the private keys 112 a, 112 b to thefinancial records, the key execution module 206 may communicaterespective data pertaining to the successfully exchange of the privatekeys 112 a, 112 b to the transaction execution module 208. Upondetermining the successful exchange of private keys 112 a, 112 brespectively associated with the sender 106 and the recipient 108 andthe encryption of the private keys 112 a, 112 b to the financial recordsassociated with the financial transaction between the sender 106 and therecipient 108, the transaction execution module 208 may be configured todetermine that the financial transaction is securely validated and maydesignate the financial transaction as a secure transaction between thesender 106 and the recipient 108. The transaction execution module 208may thereby communicate transaction data to the blockchain to allow theblockchain technology to mine the transaction and verify it towardspayment.

In particular, once the private keys 112 a, 112 b are exchanged, thetransaction execution module 208 may be configured to communicate withthe processor 118 to receive the randomly encrypted passcode that may beutilized as a particular instance of time to access the secure encrypteddata environment 122. Upon accessing the secure encrypted dataenvironment 122, the transaction execution module may be configured toaccess the secure wallet 110 previously processed and stored on thesecure encrypted data environment by the secure wallet processing module204. The transaction execution module 208 may be configured to analyzethe secure wallet 110 to obtain the transaction data (e.g., monetaryamount to be transferred) previously stored upon the secure wallet 110by the secure wallet processing module 204 to be further communicated tothe blockchain technology provider(s) through communications between thecommunication unit 126 of the secure server 102 and the blockchaininfrastructure 116. Upon accessing and analyzing the secure wallet 110and obtaining the transaction data, the transaction execution module 208may communicate data pertaining to the transaction data to the keyexecution module 206.

In one embodiment, the key execution module 206 may be configured toutilize the encrypted key generator 128 to process a public key 114 thatmay be passed to the blockchain technology provider(s) through theblockchain infrastructure 116. The public key may include informationpertaining to account information associated with the sender 106 and/orthe recipient 108 which may be encrypted using an elliptical curveprocess. In one configuration, the public key may include some selectinformation (e.g., user information) from the private keys 112 a, 112 band may be passed to the blockchain infrastructure 116 based onutilization of the communication unit 126 by the key execution module206. Upon the generation of the public key 114 by the encrypted keygenerator 128, the key execution module 206 may store the public key onthe secure encrypted data environment 122 and may communicate datapertaining to the storage of the public key 114 to the transactionexecution module 208.

In an exemplary embodiment, the transaction execution module 208 may beconfigured to communicate with the processor 118 to receive the randomlyencrypted passcode that may be utilized as a particular instance of timeto access the secure encrypted data environment 122. Upon accessing thesecure encrypted data environment 122, the transaction execution module208 may retrieve the public key 114 and may utilize the communicationunit 126 of the secure server 102 to communicate the transaction dataand public key to the blockchain infrastructure 116.

Accordingly, transaction data associated with the financial transactionbetween the sender 106 and the recipient 108 may be further verifiedthrough the blockchain technologies to complete the secure transactionand secure payment of funds from the sender 106 to the recipient 108.The blockchain infrastructure 116 may communicate a confirmation to thetransaction execution module 208 of the blockchain verification. Uponthe receipt of the confirmation, the transaction execution module 208may confirm the transaction has been securely completed. Accordingly,the secure transaction application 104 may ensure that the securetransaction between the sender 106 and the recipient 108 is securelyvalidated from an initiation point to a final payment point.

FIG. 3 is a process flow diagram of a method 300 for securing afinancial transaction between the sender 106 and the recipient 108according to an exemplary embodiment of the present disclosure. FIG. 3will be described with reference to the components of FIG. 1 and FIG. 2,through it is appreciated that the method 300 of FIG. 3 may be used withadditional and/or alternative system components. The method 300 maybegin at block 302, wherein the method 300 may include receiving aninput for a new financial transaction.

As discussed above, the transaction initiation module 202 of the securetransaction application 104 may be configured to present a securetransaction initiation user interface that may be utilized by the sender106 and/or the recipient 108 to initiate a secure transaction. Duringthe initial and subsequent uses of the secure transaction application104, the secure transaction initiation user interface may allow thesender 106 to input a monetary transfer amount (e.g., dollar amount)that the sender 106 may wish to transfer to the recipient 108. In someconfigurations, the transaction initiation module 202 may also presentthe transfer amount inputted by the sender 106 or the recipient 108 toaccept or deny the transfer of funds.

The method 300 may proceed to block 304, wherein the method 300 mayinclude processing a secure wallet 110. In an exemplary embodiment, uponthe initiation of the financial transaction between the sender 106 andthe recipient 108, the secure wallet processing module 204 may beconfigured to process the secure wallet 110 that may be associated withthe particular financial transaction. As discussed above, the securewallet 110 may be configured as an encrypted data packet that may storetransaction data associated with funds that may be transferred from thesender 106 to the recipient 108. In one embodiment, upon processing thesecure wallet 110, the secure wallet processing module 204 may beconfigured to store the secure wallet 110 within the secure encrypteddata environment 122 stored on memory 120 of the secure server 102 to besubsequently accessed upon secure validation of the financialtransaction.

The method 300 may proceed to block 306, wherein the method 300 mayinclude collecting transaction information and storing transaction datawithin the secure wallet 110. In one embodiment, the secure walletprocessing module 204 may be configured to collect transactioninformation associated with the monetary transfer amount (e.g., dollaramount) that the sender 106 may wish to transfer to the recipient 108.Additionally, the secure wallet processing module 204 may be configuredto collect data associated with one or more linked financial accountsthat may be associated with the sender 106 and the recipient 108 fromthe user profiles 130 a, 130 b stored within the user data repository124.

The method 300 may proceed to block 308, wherein the method 300 mayinclude generating a private key 112 a for the sender 106 and a privatekey 112 b for the recipient 108 of the financial transaction. In anexemplary embodiment, the key execution module 206 of the securetransaction application 104 may utilize the encrypted key generator 128to generate the private key 112 a that may be associated with the sender106 and the private key 112 b that may be associated with the recipient108. The encrypted key generator 128 may electronically generate theprivate keys 112 a, 112 b with a numerical encrypted key code or analpha numerical encrypted key code that may not be publicallyaccessible.

The method 300 may proceed to block 310, wherein the method 300 mayinclude passing the private keys 112 a, 112 b associated with the sender106 and the recipient 108 for secure validation of the financialtransaction. In an exemplary embodiment, upon the generation of theprivate keys 112 a, 112 b, the key execution module 206 may beconfigured to exchange the private keys 112 a, 112 b as ownershipcredentials to securely validate the financial transaction as a securetransaction between the sender 106 and the recipient 108. In oneconfiguration, the key execution module 206 may utilize thecommunication unit 126 to transfer the sender's private key 112 a to therecipient 108 to be authenticated without the sender 106 and/or therecipient 108 being able to view the private key 112 a. Likewise, thekey execution module 206 may utilize the communication unit 126 totransfer the recipient's private key to the sender 106 to beauthenticated without the sender 106 and/or the recipient 108 being ableto view the private key 112 b. The key execution module 206 may also beconfigured to encrypt the respective private keys 112 a, 112 b tofinancial records that are associated with the financial transaction.

The method 300 may proceed to block 312, wherein the method 300 mayinclude communicating transaction data to complete the transaction usingblockchain. In an exemplary embodiment, upon the exchange of privatekeys 112 a, 112 b and the encryption of the private keys 112 a, 112 b tothe financial records that are associated with the financialtransaction, the transaction execution module 208 may be configured todesignate the financial transaction as a secure transaction between thesender 106 and the recipient 108.

In one embodiment, upon designated the financial transaction as a securetransaction, the transaction execution module 208 may be configured toaccess the secure wallet 110 stored within the secure encrypted dataenvironment 122. The transaction execution module 208 may be configuredto analyze the secure wallet 110 stored upon the secure encrypted dataenvironment 122 to retrieve the transaction data to be furthercommunicated to the blockchain.

In one configuration, the key execution module 206 may be configured toutilize the encrypted key generator 128 to process a public key 114 thatmay be passed to the blockchain technology provider(s). Upon theprocessing of the public key 114, the key execution module 206 may storethe public key 114 upon the secure encrypted data environment 122. Inone embodiment, the key execution module 206 may access the public key114 and may update the public key 114 with transaction data associatedwith the financial transaction between the sender 106 and the recipient108. In some configurations, the key execution module 206 may beconfigured to update the public key 114 with some select information(e.g., user information) from the private keys 112 a, 112 b.

In an exemplary embodiment, upon the processing and updating of thepublic key 114, the transaction execution module 208 may be configuredto pass the public key 114 to the blockchain infrastructure 116 to passthe financial transaction through the blockchain technology to completethe secure transaction in an encrypted and secure manner usingblockchain. In particular, the transaction execution module 208 may beconfigured to utilize the communication unit 126 of the secure server102 to communicate the transaction data and the public key 114 to theblockchain infrastructure 116.

The transaction data associated with the financial transaction betweenthe sender 106 and the recipient 108 may be further verified throughblockchain technologies to complete secure payment of funds from one ormore financial accounts associated with the sender 106 to one or morefinancial accounts associated with the recipient 108. Accordingly, thesecure transaction application 104 may ensure that the financialtransaction between the sender 106 and the recipient 108 is securelyvalidated from an initiation point to a final payment point.

FIG. 4 is a process flow diagram of a method 400 for secure a privatekey transaction with blockchain according to an exemplary embodiment ofthe present disclosure. FIG. 4 will be described with reference to thecomponents of FIG. 1 and FIG. 2, through it is to be appreciated thatthe method 400 of FIG. 4 may be used with additional and/or alternativesystem components. The method 400 may begin at block 402, wherein themethod 400 may include receiving an input for initiating a financialtransaction between a sender 106 and a recipient 108.

The method 400 may proceed to block 404, wherein the method 400 mayinclude processing a secure wallet 110 that includes transaction dataassociated with the financial transaction. The method 400 may proceed toblock 406, wherein the method 400 may include generating a private key112 a for the sender 106 and a private key 112 b for the recipient 108.In one embodiment, the private keys 112 a, 112 b are securely exchangedfor secure validation of the financial transaction. The method 400 mayproceed to block 408, wherein the method 400 may include communicatingthe transaction data to complete the financial transaction using theblockchain.

It should be apparent from the foregoing description that variousexemplary embodiments of the disclosure may be implemented in hardware.Furthermore, various exemplary embodiments may be implemented asinstructions stored on a non-transitory machine-readable storage medium,such as a volatile or non-volatile memory, which may be read andexecuted by at least one processor to perform the operations describedin detail herein. A machine-readable storage medium may include anymechanism for storing information in a form readable by a machine, suchas a personal or laptop computer, a server, or other computing device.Thus, a non-transitory machine-readable storage medium excludestransitory signals but may include both volatile and non-volatilememories, including but not limited to read-only memory (ROM),random-access memory (RAM), magnetic disk storage media, optical storagemedia, flash-memory devices, and similar storage media.

It should be appreciated by those skilled in the art that any blockdiagrams herein represent conceptual views of illustrative circuitryembodying the principles of the disclosure. Similarly, it will beappreciated that any flow charts, flow diagrams, state transitiondiagrams, pseudo code, and the like represent various processes whichmay be substantially represented in machine readable media and soexecuted by a computer or processor, whether or not such computer orprocessor is explicitly shown.

It will be appreciated that various implementations of theabove-disclosed and other features and functions, or alternatives orvarieties thereof, may be desirably combined into many other differentsystems or applications. Also that various presently unforeseen orunanticipated alternatives, modifications, variations or improvementstherein may be subsequently made by those skilled in the art which arealso intended to be encompassed by the following claims.

1. A computer-implemented method for securing a private key transactionwithin blockchain comprising: receiving an input for initiating afinancial transaction between a sender and a recipient; processing asecure wallet that includes transaction data associated with thefinancial transaction; generating a private key for the sender and aprivate key for the recipient, wherein the private keys are securelyexchanged for secure validation of the financial transaction; andcommunicating the transaction data to complete the financial transactionusing the blockchain.
 2. The computer-implemented method of claim 1,wherein receiving the input for initiating the financial transactionincludes presenting a user interface to the sender and the recipient,wherein the user interface allows the sender to input a monetarytransfer amount to be transferred to the recipient.
 3. Thecomputer-implemented method of claim 2, wherein processing the securewallet includes determining that the recipient approves the monetarytransfer amount and processing the secure wallet as an encrypted datapacket that is configured to store the transaction data.
 4. Thecomputer-implemented method of claim 2, wherein processing the securewallet includes accessing a secure encrypted data store and storing thesecure wallet within the secure encrypted data store, wherein the secureencrypted data is accessible based on a selectively and randomlyencrypted passcode.
 5. The computer-implemented method of claim 2,wherein processing the secure wallet includes collecting transactioninformation associated with the monetary transfer amount and dataassociated with at least one linked financial account and storingtransaction data that includes the transaction information within thesecure wallet.
 6. The computer-implemented method of claim 1, whereingenerating the private key includes utilizing an encrypted key generatorto generate the private keys, wherein the private keys are generatedwith a numerical encrypted key code.
 7. The computer-implemented methodof claim 1, further including passing the private key associated withthe sender and the private key associated with the recipient for thesecure validation of the financial transaction.
 8. Thecomputer-implemented method of claim 1, further including generating apublic key that is passed through the blockchain to complete thefinancial transaction.
 9. The computer-implemented method of claim 8,wherein communicating the transaction data to complete the financialtransaction includes communicating the transaction data and the publickey to a blockchain infrastructure to complete the financialtransaction.
 10. A system for securing a private key transaction withinblockchain comprising: a memory storing instructions when executed by aprocessor cause the processor to: receive an input for initiating afinancial transaction between a sender and a recipient; process a securewallet that includes transaction data associated with the financialtransaction; generate a private key for the sender and a private key forthe recipient, wherein the private keys are securely exchanged forsecure validation of the financial transaction; and communicate thetransaction data to complete the financial transaction using theblockchain.
 11. The system of claim 10, wherein receiving the input forinitiating the financial transaction includes presenting a userinterface to the sender and the recipient, wherein the user interfaceallows the sender to input a monetary transfer amount to be transferredto the recipient.
 12. The system of claim 11, wherein processing thesecure wallet includes determining that the recipient approves themonetary transfer amount and processing the secure wallet as anencrypted data packet that is configured to store the transaction data.13. The system of claim 11, wherein processing the secure walletincludes accessing a secure encrypted data store and storing the securewallet within the secure encrypted data store, wherein the secureencrypted data stories accessible based on a selectively and randomlyencrypted passcode.
 14. The system of claim 11, wherein processing thesecure wallet includes collecting transaction information associatedwith the monetary transfer amount and data associated with at least onelinked financial account and storing transaction data that includes thetransaction information within the secure wallet.
 15. The system ofclaim 10, wherein generating the private key includes utilizing anencrypted key generator to generate the private keys, wherein theprivate keys are generated with a numerical encrypted key code.
 16. Thesystem of claim 10, further including passing the private key associatedwith the sender and the private key associated with the recipient forthe secure validation of the financial transaction.
 17. The system ofclaim 10, further including generating a public key that is passedthrough the blockchain to complete the financial transaction.
 18. Thesystem of claim 17, wherein communicating the transaction data tocomplete the financial transaction includes communicating thetransaction data and the public key to a blockchain infrastructure tocomplete the financial transaction.
 19. A non-transitory computerreadable storage medium storing instructions that when executed by acomputer, which includes a processor perform a method, the methodcomprising: receiving an input for initiating a financial transactionbetween a sender and a recipient; processing a secure wallet thatincludes transaction data associated with the financial transaction;generating a private key for the sender and a private key for therecipient, wherein the private keys are securely exchanged for securevalidation of the financial transaction; and communicating thetransaction data to complete the financial transaction using theblockchain.
 20. The non-transitory computer readable storage medium ofclaim 19, further including generating a public key that is passedthrough the blockchain to complete the financial transaction.